Change for Chrome DevTools to stop raising issues for pagination fields#4876
Open
victorprosa wants to merge 1 commit intoolifolkerd:masterfrom
Open
Change for Chrome DevTools to stop raising issues for pagination fields#4876victorprosa wants to merge 1 commit intoolifolkerd:masterfrom
victorprosa wants to merge 1 commit intoolifolkerd:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, Chrome DevTools raises issues for tabulator tables with page size selection due to a lack of relation between the select input and it's label:
According to MDN, the recommended aproach is to always link the form and label elements with a "for" property, mainly due to accessibility:
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/label
Even if it's debatable whether DevTools should be raising these issues, trying to keep the browser issues list empty and following the best practices for accessibility, I propose this PR as a low priority minor annoyance fix that doesn't affect functionality.